This PR addresses a critical issue in the .github/workflows/release.yml CI pipeline where downstream jobs, including tests and builds, were being skipped on push events.

The root cause was the goreleaser job's dependency on dep-guard. Since dep-guard is configured to run only on pull_request events, it was skipped on push, causing GitHub Actions to transitively skip goreleaser and all subsequent jobs.

This fix decouples goreleaser from dep-guard, ensuring the main workflow runs on push events. To maintain dependency validation for pull requests, dep-guard is now a direct dependency of the final aggregator job. Additionally, the conditional logic for several jobs has been updated to explicitly check for the successful completion of their dependencies (needs.<job>.result == 'success') and use !cancelled() for more robust execution flow.

Files Changed Analysis

• .github/workflows/release.yml: The sole file modified. Changes involve altering job dependencies and strengthening the conditional if statements for multiple jobs to ensure they run only when their dependencies have succeeded.

Architecture & Impact Assessment

• What this PR accomplishes: It restores the integrity of the CI pipeline by ensuring that all test, build, and release jobs execute as expected on push events to release branches, preventing untested code from being promoted.
• Key technical changes introduced:
  1. The dependency of goreleaser on dep-guard is removed.
  2. The aggregator job now directly depends on dep-guard, ensuring dependency checks are still mandatory for merging pull requests.
  3. Conditional execution (if clauses) for multiple jobs are now more explicit, checking needs.<job>.result == 'success'.
• Affected system components: The CI/CD workflow defined in release.yml. This change directly impacts the reliability of the automated testing and release process.

Job Dependency Change (on pull_request)

The core logic change for pull request validation is visualized below.

Before:

graph TD
    A[dep-guard] --> B[goreleaser]
    B --> C[aggregator]
    D[api-tests] --> C

After:

graph TD
    A[dep-guard] --> C[aggregator]
    B[goreleaser] --> C
    D[api-tests] --> C

Scope Discovery & Context Expansion

• The scope of this change is localized to the release.yml workflow configuration file.
• However, its impact is significant for the repository's development lifecycle. By fixing the CI pipeline, it ensures that all code pushed to release branches undergoes the full suite of automated checks, which is fundamental for maintaining code quality and release stability.

Powered by Visor from Probelabs

Last updated: 2026-04-17T08:55:49.393Z | Triggered by: pr_updated | Commit: c6c1536

💡 TIP: You can chat with Visor using /visor ask <your question>

✅ Architecture Check Passed

No architecture issues found – changes LGTM.

✅ Performance Check Passed

No performance issues found – changes LGTM.

✅ Quality Check Passed

No quality issues found – changes LGTM.

Powered by Visor from Probelabs

Last updated: 2026-04-17T08:55:41.618Z | Triggered by: pr_updated | Commit: c6c1536

💡 TIP: You can chat with Visor using /visor ask <your question>

API Changes

no api changes detected

Quality Gate failed

Failed conditions
1 Security Hotspot
C Security Rating on New Code (required ≥ A)

See analysis details on SonarQube Cloud

Catch issues before they fail your Quality Gate with our IDE extension SonarQube for IDE

🚨 Jira Linter Failed

Commit: c6c1536
Failed at: 2026-04-17 08:54:43 UTC

The Jira linter failed to validate your PR. Please check the error details below:

failed to validate branch and PR title rules: branch name 'fix/dep-guard-skip-release-5.12' must contain a valid Jira ticket ID (e.g., ABC-123)

Next Steps

• Ensure your branch name contains a valid Jira ticket ID (e.g., ABC-123)
• Verify your PR title matches the branch's Jira ticket ID
• Check that the Jira ticket exists and is accessible

This comment will be automatically deleted once the linter passes.